Bug: TenanAwareKey vs not tenant aware keys in cache #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello @rbygrave ,
@rPraml and I tested our application in a multi tomcat environment with hazelcast and we got some problems by caching (login of a user).
From an user-password entity we had 2 entries in the cache map: one with the UUID as key (e.g. 1234) and the second one used the TenantAwareKey (e.g. 1234:1, :1 as the tenant information) --> Our next query wanted to load the entity from the cache but it got the "wrong" one without the tenant information which was outdated (--> our login was not successful because it used the old password).
@rPraml implemented a temporary solution that works in our application.